A panel of ThoughtWorks and industry practitioners walks through the operational failures of deploying agentic AI, from silent semantic errors to code review that can't keep pace with agent output. It also covers how to limit damage through agent identity, access controls, and continuous evals.

• Embedding drift in a financial compliance agent caused false positive and false negative spikes after an unannounced background model update, while every infrastructure health check stayed green.
• Coding agents produce code faster than humans can review line by line, so teams should automate style and syntax checks in CI/CD and reserve human review for architecture, business intent, and non-functional requirements.
• Treat each agent like a new engineering hire: give it its own non-human identity, separate read-only from write actions, version third-party MCP dependencies, and keep API secrets outside its runtime.